Technologies for quality of service based throttling in fabric architectures

ABSTRACT

Technologies for quality of service based throttling in a fabric architecture include a network node of a plurality of network nodes interconnected across the fabric architecture via an interconnect fabric. The network node includes a host fabric interface (HFI) configured to facilitate the transmission of data to/from the network node, monitor quality of service levels of resources of the network node used to process and transmit the data, and detect a throttling condition based on a result of the monitored quality of service levels. The HFI is further configured to generate and transmit a throttling message to one or more of the interconnected network nodes in response to having detected a throttling condition. The HFI is additionally configured to receive a throttling message from another of the network nodes and perform a throttling action on one or more of the resources based on the received throttling message. Other embodiments are described herein.

BACKGROUND

Demands by individuals, researchers, and enterprises for increasedcompute performance and storage capacity of computing devices haveresulted in various computing technologies developed to address thosedemands. For example, compute intensive applications, such as enterprisecloud-based applications (e.g., software as a service (SaaS)applications), data mining applications, data-driven modelingapplications, scientific computation problem solving applications, etc.,typically rely on complex, large-scale computing environments (e.g.,high-performance computing (HPC) environments, cloud computingenvironments, etc.) to execute the compute intensive applications, aswell as store voluminous amounts of data. Such large-scale computingenvironments can include tens of hundreds (e.g., enterprise systems) totens of thousands (e.g., HPC systems) of multi-processor/multi-corenetwork nodes connected via high-speed interconnects (e.g., fabricinterconnects in a unified fabric).

To carry out such processor intensive computations, various computingtechnologies have been implemented to distribute workloads acrossdifferent network computing devices, such as parallel computing,distributed computing, etc. In support of such distributed workloadoperations, multiprocessor hardware architecture (e.g., multiplemulti-core processors that share memory) has been developed tofacilitate multiprocessing (i.e., coordinated, simultaneous processingby more than one processor) across local and remote shared memorysystems using various parallel computer memory design architectures,such as non-uniform memory access (NUMA), and other distributed memoryarchitectures.

Accordingly, memory requests from multiple interconnected network nodescan occupy the same shared buffer (e.g., super queues, table ofrequests, etc.) as local memory requests of a particular network node.However, such shared buffers are limited in size (e.g., containing tensof entries), which can result in other memory requests being queueduntil data returns from the memory subsystems for those memory requestspresently in the shared buffer. As such, entries of the shared bufferstend to be occupied by those memory requests targeting memory thatprovides high latency access (e.g., memory requests received from remotenetwork nodes) or that is being over-utilized. As a result, otherrequests (e.g., local memory requests) targeting faster or non-congestedmemory (i.e., memory requests that would be served faster) can becomestarved in the core due to no available shared buffer entries availableto execute said memory requests.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and notby way of limitation in the accompanying figures. For simplicity andclarity of illustration, elements illustrated in the figures are notnecessarily drawn to scale. Where considered appropriate, referencelabels have been repeated among the figures to indicate corresponding oranalogous elements.

FIG. 1 is a simplified block diagram of at least one embodiment of asystem for quality of service based throttling in a fabric architectureincludes multiple interconnected network nodes communicatively coupledvia an interconnect fabric;

FIG. 2 is a simplified block diagram of at least one embodiment of oneof the network nodes of the system of FIG. 1 ;

FIG. 3 is a simplified block diagram of another embodiment of thenetwork node of FIG. 2 ;

FIG. 4 is a simplified block diagram of at least one embodiment of anenvironment that may be established by the network node of FIG. 2 ;

FIG. 5 is a simplified flow diagram of at least one embodiment of amethod for processing a local memory request from a remote network nodethat may be executed by the network node of FIG. 2 ;

FIG. 6 is a simplified flow diagram of at least one embodiment of amethod for accessing memory of a remote network node that may beexecuted by the network node of FIG. 2 ;

FIG. 7 is a simplified flow diagram of at least one embodiment of amethod for generating throttling messages for external transmission toone or more remote network nodes that may be executed by the networknode of FIG. 2 ; and

FIG. 8 is a simplified flow diagram of at least one embodiment of amethod for processing throttling messages received from a remote networknode that may be executed by the network node of FIG. 2 .

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific embodiments thereof havebeen shown by way of example in the drawings and will be describedherein in detail. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,”“an illustrative embodiment,” etc., indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but every embodiment may or may not necessarily includethat particular feature, structure, or characteristic. Moreover, suchphrases are not necessarily referring to the same embodiment. Further,when a particular feature, structure, or characteristic is described inconnection with an embodiment, it is submitted that it is within theknowledge of one skilled in the art to effect such feature, structure,or characteristic in connection with other embodiments whether or notexplicitly described. Additionally, it should be appreciated that itemsincluded in a list in the form of “at least one of A, B, and C” can mean(A); (B); (C): (A and B); (A and C); (B and C); or (A, B, and C).Similarly, items listed in the form of “at least one of A, B, or C” canmean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).

The disclosed embodiments may be implemented, in some cases, inhardware, firmware, software, or any combination thereof. The disclosedembodiments may also be implemented as instructions carried by or storedon one or more transitory or non-transitory machine-readable (e.g.,computer-readable) storage media (e.g., memory, data storage, etc.),which may be read and executed by one or more processors. Amachine-readable storage medium may be embodied as any storage device,mechanism, or other physical structure for storing or transmittinginformation in a form readable by a machine (e.g., a volatile ornon-volatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown inspecific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

Referring now to FIG. 1 , in an illustrative embodiment, a system 100for quality of service based throttling in a fabric architectureincludes multiple interconnected network nodes 102 communicativelycoupled via an interconnect fabric 114. The illustrative system 100includes various types of network nodes 102 including multiple computenodes 104 and storage nodes 112. The illustrative compute nodes 104include a first compute node, which is designated as compute node (1)106, a second compute node, which is designated as compute nodes (2)108, and a third compute node, which is designated as compute nodes (N)110 (i.e., the “Nth” compute node of the compute nodes 104, wherein “N”is a positive integer and designates one or more additional computenodes 104). It should be appreciated that, in other embodiments, theremay be any number of compute nodes 104 and/or storage nodes 112.Illustratively, the interconnect fabric 114 includes a network switch116 and a number of fabric interconnects 118 for communicativelycoupling the network nodes 102. It should be appreciated, however, thatwhile only a single network switch 116 is shown, there may be any numberof network switches 116 in other interconnect fabric embodiments.

In use, the network nodes 102 monitor quality of service levelsassociated with local resources (e.g., physical and/or virtualcomponents) to detect throttling conditions (e.g., congestion,saturation, over-utilization, workload distribution unfairness, etc.)associated with such resources and transmit throttling messages to othernetwork nodes 102 of the fabric architecture requesting a throttlingaction to be performed by the receiving network nodes 102 upon detectionof such throttling conditions. The throttling messages may includevarious types throttling requests directed toward throttling particularresources of a network node 102. For example, the throttling messagesmay include a memory throttle request, an I/O throttle request, anaccelerator throttle processing request, an HFI saturation throttlerequest, etc. It should be appreciated that the throttling messages aretransmitted periodically over the period of time in which the throttlingcondition is detected. In other words, the network node 102 continues totransmit throttling messages until the corresponding throttlingcondition subsides.

To do so, unlike present technologies in which the network nodes 102 donot externally transmit the throttling messages, thereby leavingthrottling restricted to being able to only throttle those resourceslocal to the network nodes 102, components of the network nodes 102 andthe associated interconnect fabric 114 are extended to transmitthrottling information (e.g., generate new throttling messages,propagate existing throttling signals, etc.) to other network nodes 102that are presently requesting access to a shared structure (e.g., ashared buffer) of the respective one of the network nodes 102 havingdetected the throttling condition.

In an illustrative example, certain coherency protocols include agententities, such as the caching agents and home agents of Intel® coherencyprotocols, are configured to initiate transactions into coherent memory(e.g., via the caching agents) and service the coherent transactions(e.g., via the home agents). Such agent entities are presentlyconfigured to detect certain conditions local to a respective one of thenetwork nodes 102 and issue local processor core throttling signals tothrottle one or more cores of the processor. However, contention infabric architectures can occur not only at the shared paths within eachof the network nodes 102, but also in shared paths of the interconnectfabric 114, such as shared buffers (e.g., super queues in the processorcore, table of requests in the caching/home agents, etc.).

In an illustrative example, the compute node (1) 106 may be accessingmemory of the compute node (2) 108, which may be configured to monitormemory access requests (e.g., memory accesses received locally, memoryaccesses received from another of the compute nodes 104, etc.) andmemory utilization level(s). Under certain conditions, the compute node(2) 108 may experience high and unequal contention due to memory requestqueue entries being occupied by requests to slower memory (e.g.,non-cache memory) of the compute node (2) 108 that have been receivedfrom the compute node (1) 106. Accordingly, under such conditions, thecompute node (2) 108 is configured to transmit a throttling message tothe compute node (1) 106 indicating that memory of the compute node (2)108 is presently saturated, which the compute node (1) can use to reducean injection rate of memory requests directed to the compute node (2)108.

In some embodiments, the network nodes 102 are configured to exposepresent node throttling techniques between different network nodes 102of the system 100 using the transport layer (i.e., Layer 4 (L4)) of theOpen Systems Interconnection (OSI) model. Accordingly, new and/orexisting throttling signals originating from one of the network nodes102 (e.g., from caching agents, home agents, input/output operations,schedulers, etc.) may be propagated over the fabric interconnects 118 toother network nodes 102, such as those requesting access to sharedstructures of the one of the network nodes 102 from which the throttlingsignals originated.

The network nodes 102 may be embodied as any type of network traffic(e.g., network packets, messages, data, etc.) computing and/or storagecomputing device that is capable of performing the functions describedherein, such as, without limitation, a server (e.g., stand-alone,rack-mounted, blade, etc.), a network appliance (e.g., physical orvirtual), a switch (e.g., rack-mounted, standalone, fully managed,partially managed, full-duplex, and/or half-duplex communication modeenabled, etc.), a router, a web appliance, a distributed computingsystem, and/or a multiprocessor-based system. As described previously,the illustrative network nodes 102 include compute nodes 104 and storagenodes 112; however, it should be appreciated that the network nodes 102may include additional and/or alternative network nodes, such ascontroller nodes, network nodes, utility nodes, etc., which are notshown to preserve clarity of the description.

As shown in FIG. 2 , an illustrative network node 102 includes a firstprocessor, designated as processor (1) 202, a second processor,designated as processor (2) 208, an input/output (I/O) subsystem 214, amain memory 216, a data storage device 218, and communication circuitry220. It should be appreciated that the compute nodes 104 and/or storagenodes 112 of FIG. 1 may include the components described in FIG. 2 ofthe illustrative network node 102.

Of course, the network node 102 may include other or additionalcomponents, such as those commonly found in a computing device, in otherembodiments. Additionally, in some embodiments, one or more of theillustrative components may be incorporated in, or otherwise form aportion of, another component. For example, the cache memory 206, orportions thereof, may be incorporated in one or both of the processors202, 208 in some embodiments. Further, in some embodiments, one or moreof the illustrative components may be omitted from the network node 102.For example, although the illustrative network node 102 includes twoprocessors 202, 208, the network node 102 may include a greater numberof processors, in other embodiments.

Each of the processors 202, 208 (i.e., physical processor packages) maybe embodied as any type of multi-core processor capable of performingthe functions described herein, such as, but not limited to, a singlephysical multi-processor core chip, or package. The illustrativeprocessor (1) 202 includes a number of processor cores 204, while theillustrative processor (2) 208 similarly includes a number of processorcores 210. As described previously, each of the processors 202, 208includes more than one processor cores (e.g., 2 processors cores, 4processors cores, 8 processors cores, 16 processors cores, etc.).

Each of processor cores 204, 210 is embodied as an independent logicalexecution unit capable of executing programmed instructions. In someembodiments, the processor cores 204, 210 may include a portion of cachememory (e.g., an L1 cache) and functional units usable to independentlyexecute programs or threads. It should be appreciated that in someembodiments of the network node 102, such as supercomputers, the networknode 102 may include thousands of processor cores. Each of theprocessors 202, 208 may be connected to a physical connector, or socket,on a motherboard (not shown) of the network node 102 configured toaccept a single physical processor package (i.e., a multi-core physicalintegrated circuit).

The illustrative processor (1) 202 additionally includes a cache memory206. Similarly, the illustrative processor (2) 208 also includes a cachememory 212. Each cache memory 206, 212 may be embodied as any type ofcache that the respective processor 202, 208 can access more quicklythan the main memory 216, such as an on-die cache, or on-processorcache. In other embodiments, the cache memory 206, 212 may be an off-diecache, but reside on the same system-on-a-chip (SoC) as the respectiveprocessor 202, 208. It should be appreciated that, in some embodiments,the cache memory 206, 212 may have a multi-level architecture. In otherwords, in such multi-level architecture embodiments, the cache memory206, 212 may be embodied as an L1, L2, or L3 cache, for example.

The main memory 216 may be embodied as any type of volatile ornon-volatile memory or data storage device capable of performing thefunctions described herein. In operation, the main memory 216 may storevarious data and software used during operation of the network node 102,such as operating systems, applications, programs, libraries, anddrivers. The main memory 216 is communicatively coupled to theprocessors 202, 208 via the I/O subsystem 214, which may be embodied ascircuitry and/or components to facilitate input/output operations withthe processors 202, 208, the main memory 216, and other components ofthe network node 102. For example, the I/O subsystem 214 may be embodiedas, or otherwise include, memory controller hubs, input/output controlhubs, firmware devices, communication links (i.e., point-to-point links,bus links, wires, cables, light guides, printed circuit board traces,etc.) and/or other components and subsystems to facilitate theinput/output operations. In some embodiments, the I/O subsystem 214 mayform a portion of a SoC and be incorporated, along with one or both ofthe processors 202, 208, the main memory 216, and/or other components ofthe network node 102, on a single integrated circuit chip.

The data storage device 218 may be embodied as any type of device ordevices configured for short-term or long-term storage of data such as,for example, memory devices and circuits, memory cards, hard diskdrives, solid-state drives, or other data storage devices. It should beappreciated that the data storage device 218 and/or the main memory 216(e.g., the computer-readable storage media) may store various data asdescribed herein, including operating systems, applications, programs,libraries, drivers, instructions, etc., capable of being executed by aprocessor (e.g., the processor 202, the processor 208, etc.) of thenetwork node 102.

The communication circuitry 220 may be embodied as any communicationcircuit, device, or collection thereof, capable of enablingcommunications between the network node 102 and other computing devices(e.g., a compute node 104, a storage node 112, etc.) over a network. Thecommunication circuitry 220 may be configured to use any one or morecommunication technologies (e.g., wireless or wired communicationtechnologies) and associated protocols (e.g., Internet Protocol (IP),Ethernet, Bluetooth®, WiMAX, LTE, 5G, etc.) to effect suchcommunication.

The illustrative communication circuitry 220 includes a host fabricinterface (HFI) 222. The HFI 222 may be embodied as one or moreadd-in-boards, daughtercards, network interface cards, controller chips,chipsets, or other devices that may be used by the network node 102. Forexample, in some embodiments, the HFI 222 may be integrated with one orboth of the processors 202, 208 (e.g., on a coherent fabric within oneor both of the processors 202, 208), embodied as an expansion cardcoupled to the I/O subsystem 214 over an expansion bus (e.g., PCIExpress (PCIe)), part of a SoC that includes one or more processors, orincluded on a multichip package that also contains one or moreprocessors. Additionally or alternatively, in some embodiments,functionality of the HFI 222 may be integrated into one or morecomponents of the network node 102 at the board level, socket level,chip level, and/or other levels. The HFI 222 is configured to facilitatethe transfer to data/messages to enable tasks executing on theprocessors 202, 208 to access shared structures (e.g., shared physicalmemory) of the other network nodes 102, such as may be necessary duringparallel or distributed computing operations.

It should be appreciated that those network nodes 102 implemented asstorage nodes 112 may generally include more data storage device 218capacity than those network nodes 102 implemented as compute nodes 104.Similarly, it should also be appreciated that those network nodes 102implemented as compute nodes 104 may generally include more processorcapability that those network nodes 102 implemented as storage nodes112. In other words, the storage nodes 112 may be embodied as physicalservers including numerous hard-disk drives (HDDs) or solid-state drives(SDDs) relative to the number of storage devices of the compute nudes104, whereas the compute nodes 104 may be embodied as physical serversincluding numerous processors having multiple cores relative to thenumber of processors of the storage nodes 112. However, it should befurther appreciated that any of the network nodes 102 may be implementedas a compute node 104 and/or a storage node 112, regardless of thecomponent configuration relative to the other network nodes 102.

Referring again to FIG. 1 , the interconnect fabric 114, illustrativelythe combination of the network switch 116 and the fabric interconnects118, may be embodied as one or more buses, switches, and/or networksconfigured to support transmission of network traffic as a function ofvarious interconnect protocols and/or network protocols. In use, theinterconnect fabric 114 is utilized by the network nodes 102 (e.g., viarespective HFIs 222) to communicate with the other network nodes 102(i.e., across the interconnect fabric 114). Accordingly, the networkswitch 116 may be embodied as any type of switching device (e.g., acrossbar switch) capable of network traffic forwarding via the fabricinterconnects 118 in a switched, or switching, fabric architecture.

Referring now to FIG. 3 , in an illustrative embodiment, the networknode 102 of FIG. 2 includes one or more non-uniform memory access (NUMA)domains 300 communicatively coupled to the HFI 222. The illustrativeNUMA domains 300 include a first NUMA domain, designated as NUMA domain(1) 302, and a second NUMA domain, designated as NUMA domain (2) 308.Each of the NUMA domains 300 includes a number of allocated processorcores of a physical processor package, referred to herein as aprocessor. As shown in the illustrative embodiment, the NUMA domain (1)302 includes the processor cores 204 of processor (1) 202 and the NUMAdomain (2) 308 includes the processor cores 210 of processor (2) 208.However, it should be appreciated that, in some embodiments, theprocessor cores 204 of the processor 202 and/or the processor cores 210of the processor 208 may be divided and each set of divided processorcores may be allocated to a different NUMA domain 300. It should beappreciated that each set of allocated processor cores assigned to arespective one of the NUMA domains 300 may be referred to as socketcores. In other words, the number of allocated cores of a physicalprocessor package may be referred to as a socket.

Additionally, each of the NUMA domains 300 corresponds to a particularmemory type (e.g., double data rate (DDR) memory, disk, etc.) andincludes a portion of that memory type of local memory (e.g., the mainmemory 216), which has been allocated to the processor cores of therespective NUMA domain 300. Further, the local memory is directly linkedto the physical processor package on which the processor cores reside.In the illustrative embodiment, the NUMA domain (1) 302 includes a localmemory (1) 304 and the NUMA domain (2) 308 includes a local memory (2)310. In some embodiments, data may be transmitted between the NUMAdomains 300 via an interconnect 314 (e.g., an Intel® UltraPathInterconnect (UPI), an Intel® QuickPath Interconnect (QPI), an AMD®Unified Media Interface (UMI) interconnect, or the like). The localmemory of one of the NUMA domains 300 is considered to be remote, orforeign, relative to the other NUMA domains 300. Accordingly, it shouldbe appreciated that network traffic transmitted across the interconnect314 may introduce load/contention, increase overall bandwidth usage, andreduce latency associated with accesses to remote memory, as compared todata being processed using the local memory.

Each of the illustrative processors 202, 208 additionally includes anon-die interconnect (e.g., the on-die interconnect 306 of the processor202 and the on-die interconnect 312 of the processor 208) configured tointerface with the HFI 222 via point-to-point interfaces 316 capable offacilitating the transfer of data between the HFI 222 and the processors202, 208. In some embodiments, the NUMA domains 300 may be definedinternally in the HFI 222. In an illustrative example, one of the NUMAdomains 300 (e.g., the NUMA domain (1) 302) of one of the network nodes102 (e.g., the compute node (1) 106) may correspond to transactionsprocessed by the HFI 222 from another of the network nodes 102 (e.g.,the compute node (2) 108). Accordingly, the HFI 222 of the compute node(1) 106 can issue throttling messages to the compute node (2) 108 upon adetermination by the compute node (1) 106 that the compute node (2) 108is issuing too many requests to the compute node (1) 106. In someembodiments, such throttling messages may include information propagatedfrom caching agents of the processor 202 received by the HFI 222 via thepoint-to-point interfaces 316.

Referring now to FIG. 4 , in an illustrative embodiment, one of thenetwork nodes 102 establishes an environment 400 during operation. Theillustrative environment 400 includes a communication management module410, a quality of service (QoS) monitoring module 420, a throttlingmessage transmission module 430, a throttling message reception module440, and a throttling response execution module 450. The various modulesof the environment 400 may be embodied as hardware, firmware, software,or a combination thereof. As such, in some embodiments, one or more ofthe modules of the environment 400 may be embodied as circuitry orcollection of electrical devices (e.g., a communication managementcircuit 410, a QoS monitoring circuit 420, a throttling messagetransmission circuit 430, a throttling message reception circuit 440, athrottling response execution circuit 450, etc.).

It should be appreciated that, in such embodiments, one or more of thecommunication management circuit 410, the QoS monitoring circuit 420,the throttling message transmission circuit 430, the throttling messagereception circuit 440, and the throttling response execution circuit 450may form a portion of one or more processors (e.g., processor (1) 202and processor (2) 208 of FIG. 2 ), the I/O subsystem 214, thecommunication circuitry 220, and/or other components of the networknodes 102. Additionally, in some embodiments, one or more of theillustrative modules may form a portion of another module and/or one ormore of the illustrative modules may be independent of one another.Further, in some embodiments, one or more of the modules of theenvironment 400 may be embodied as virtualized hardware components oremulated architecture, which may be established and maintained by theone or more processors and/or other components of the network nodes 102.

In the illustrative environment 400, the network node 102 furtherincludes network node data 402, monitoring result data 404, requestmonitoring data 406, and NUMA identification data 408, each of which maybe stored in the main memory 216 and/or the data storage device 218 ofthe network node 102. Further, each of the network node data 402, themonitoring result data 404, the request monitoring data 406, and theNUMA identification data 408 may be accessed by the various modulesand/or sub-modules of the network node 102. Additionally, it should beappreciated that in some embodiments the data stored in, or otherwiserepresented by, each of the network node data 402, the monitoring resultdata 404, the request monitoring data 406, and the NUMA identificationdata 408 may not be mutually exclusive relative to each other.

For example, in some implementations, data stored in the network nodedata 402 may also be stored as a portion of the monitoring result data404, and/or vice versa. As such, although the various data utilized bythe network node 102 is described herein as particular discrete data,such data may be combined, aggregated, and/or otherwise form portions ofa single or multiple data sets, including duplicative copies, in otherembodiments. It should be further appreciated that the network node 102may include additional and/or alternative components, sub-components,modules, sub-modules, and/or devices commonly found in a computingdevice, which are not illustrated in FIG. 4 for clarity of thedescription.

The communication management module 410, which may be embodied ashardware, firmware, software, virtualized hardware, emulatedarchitecture, and/or a combination thereof as discussed above, isconfigured to facilitate inbound and outbound wired and/or wirelessnetwork communications (e.g., network traffic, network packets, networkflows, etc.) to and from the network node 102. To do so, thecommunication management module 410 is configured to receive and processnetwork packets from other network nodes 102 via the interconnectfabric. Additionally, the communication management module 410 isconfigured to prepare and transmit network packets to other networknodes 102 via the interconnect fabric. Accordingly, in some embodiments,at least a portion of the functionality of the communication managementmodule 410 may be performed by the communication circuitry 220 of thenetwork node 102, or more specifically by the HFI 222 of thecommunication circuitry 220. In some embodiments, data usable tocommunicate with the other network nodes 102 of the fabric architecture,such as IP address information, flow information, etc., may be stored inthe network node data.

The QoS monitoring module 420, which may be embodied as hardware,firmware, software, virtualized hardware, emulated architecture, and/ora combination thereof as discussed above, is configured to monitorvarious characteristics of the network node 102. To do so, theillustrative QoS monitoring module 420 includes a resource utilizationmonitoring module 422, a load balancing monitoring module 424, and anHFI saturation monitoring module 426. It should be appreciated that eachof the resource utilization monitoring module 422, the load balancingmonitoring module 424, and the HFI saturation monitoring module 426 ofthe QoS monitoring module 420 may be separately embodied as hardware,firmware, software, virtualized hardware, emulated architecture, and/ora combination thereof. For example, the resource utilization monitoringmodule 422 may be embodied as a hardware component, while the loadbalancing monitoring module 424 and/or the HFI saturation monitoringmodule 426 may be embodied as a virtualized hardware component or assome other combination of hardware, firmware, software, virtualizedhardware, emulated architecture, and/or a combination thereof.

The resource utilization monitoring module 422 is configured to monitorutilization levels of the resources (i.e., physical and/or virtualcomponents) of the network node 102. In an illustrative example, theresource utilization monitoring module 422 may be configured to monitormemory utilization levels. To do so, in some embodiments, the resourceutilization monitoring module 422 may be configured to receivethrottling signals presently generated by one or more local cachingagents of a processor of the network node 102 that is usable to slowdown or otherwise reduce an injection rate to a given memory typeindicated by the throttling signals. Additionally or alternatively, theresource utilization monitoring module 422 may be configured to identifypresent usage levels of the resources to determine a saturation level ofthe monitored resources.

The load balancing monitoring module 424 is configured to monitor thedistribution of workloads across the resources (i.e., physical and/orvirtual components) of the network node 102. The HFI utilizationmonitoring module 426 is configured to monitor utilization of the HFI222. Accordingly, the HFI utilization monitoring module 426 can detect asaturation of the HFI 222 even if the resources attached thereto havenot become saturated. In an illustrative example, one of the computenodes 104 may saturate an HFI 222 of one of the storage nodes 112 whenaccessing storage devices of the storage node 112. Under suchconditions, the HFI 222 of the storage node 112 may become saturated,while the storage devices of the storage node 112 may not be fullyutilized (i.e., saturated). In some embodiments, the monitoring results(e.g., present/historical utilization values, present/historical loadbalancing information, etc.) may be stored in the monitoring result data404.

The throttling message transmission module 430, which may be embodied ashardware, firmware, software, virtualized hardware, emulatedarchitecture, and/or a combination thereof as discussed above, isconfigured to generate and transmit throttling messages to the othernetwork nodes 102. As described previously, certain conditions (i.e.,throttling conditions) may exist on the network node 102 such thatresource access requests generated by the network node 102 requestingaccess to local resources of the network node 102 may become starved dueto the other network nodes 102 maintaining an unencumbered injectionrate to resources that are locally throttled. Accordingly, unlikepresent technologies that only provide local throttling, the networknode 102 is configured to detect such throttling conditions and generatea throttling message for transmission to the other network nodes 102responsible for, or otherwise contributing to, the throttlingconditions.

To generate and transmit throttling messages to the other network nodes102, the illustrative throttling message transmission module 430includes a throttling condition detection module 432 and a transmissionmode determination module 434. It should be appreciated that each of thethrottling condition detection module 432 and the transmission modedetermination module 434 of the QoS monitoring module 420 may beseparately embodied as hardware, firmware, software, virtualizedhardware, emulated architecture, and/or a combination thereof. Forexample, the throttling condition detection module 432 may be embodiedas a hardware component, while the transmission mode determinationmodule 434 is embodied as a virtualized hardware component or as someother combination of hardware, firmware, software, virtualized hardware,emulated architecture, and/or a combination thereof.

The throttling condition detection module 432 is configured to detectwhether a throttling condition exists. To do so, the throttlingcondition detection module 432 may be configured to compare presentquality of service conditions (e.g., as may be determined by the QoSmonitoring module 420) to corresponding thresholds. For example, thethrottling condition detection module 432 may be configured to compare apresent memory utilization level against a memory saturation threshold.Accordingly, the throttling condition detection module 432 may detect athrottling condition upon a determination that the present memoryutilization level exceeds the memory saturation threshold. Additionallyor alternatively, the throttling condition detection module 432 may beconfigured to process throttling signals generated inside the networknode 102. As described previously, an agent entity (e.g., a cachingagent, a home agent, etc.) may generate local throttle requests toparticular on-die clusters, such as memory or I/O. Accordingly, thethrottling condition detection module 432 is configured to interpretsuch local throttle requests to determine whether they indicate athrottling condition whereby one or more of the other network nodes 102should be notified to take an appropriate throttling action.

The transmission mode determination module 434 is configured todetermine which transmission mode to use to transmit the throttlingmessage generated in response to a detected throttling condition, as maybe detected by the throttling condition detection module 432. To do so,the transmission mode determination module 434 is configured to detectwhich one or more of the network nodes 102 to transmit the throttlingmessage based on the identified other network node(s) 102 responsiblefor, or otherwise contributing to, the throttling condition. Forexample, the transmission mode determination module 434 may determine asingle network node 102 is issuing too many memory access requests, inwhich case the transmission mode determination module 434 may determineto transmit the generated throttling message using a unicast mode.Otherwise, if the transmission mode determination module 434 determinesmore than one of the network nodes 102 is responsible for, or otherwisecontributing to, the present throttling condition, the transmission modedetermination module 434 may determine to transmit the generatedthrottling message using a multicast mode.

As described previously, the throttling message transmission module 430is configured to transmit throttling messages requesting another networknode 102 take an action (e.g., throttle processor cores of a particularNUMA domain) in response to receipt of the throttling messages. Each ofthe NUMA domains 300 of each of the network nodes 102 has acorresponding NUMA domain identifier usable by the throttling messagetransmission module 430 to determine which NUMA domain 300 is to bethrottled. Accordingly, the network node 102 includes NUMA domainidentifiers of the NUMA domains 300 local to the network node 102 aswell as NUMA domain identifiers of the NUMA domains of the other networknodes 102. However, in some embodiments, the NUMA domain identifiers maynot be known, such as in distributed tag directory schemes. In suchembodiments, the throttling message transmission module 430 can predictwhich NUMA domain 300 the receiving network nodes 102 will perform theresponsive action.

To do so, the throttling message transmission module 430 may be furtherconfigured to predict which NUMA domain 300 a receiving network node 102will take action upon based on the principle that applications accessingNUMA domains will operate within a certain range of memory addresses inthat NUMA domain. An on-die interconnect interface (e.g., one of thepoint-to-point interfaces 316 of FIG. 3 ) of the network node 102 isconfigured to generate requests to an agent entity, such as the cachingagents. Accordingly, the on-die interconnect interface may be extendedto use a domain prediction table to determine which NUMA domaincorresponds to the throttling message, as well as whether the NUMAdomain (e.g., a processor core of the NUMA domain) is presentlydistressed (i.e., has been throttled for that NUMA domain). If acomponent of the NUMA domain is presently distressed, the throttlingmessage may not be issued (i.e., injected) to the agent entity until thedistress is no longer present and acknowledged by the agent entity.Accordingly, use of the domain prediction table may allow the networknode 102 to speculate the affected NUMA domain 300 of the other networknode 102. In some embodiments, data of the domain prediction table maybe stored in the NUMA identification data 408.

The domain prediction table may include an identifier of each agententity, a NUMA level that is known by each of the network nodes 102, alast address range (e.g., formatted as a bit mask) accessed for each ofthe NUMA domains 300 and/or agent entities, and a granularity which maybe configurable per NUMA domain 300. In an illustrative embodiment, thegranularity may be 4 GB for a particular NUMA domain 300 and a lastaddress (e.g., 0x78C9657FA) sent to a particular agent entity targetinga particular NUMA level belongs to the address range0x700000000-0x700000000+4 GB. As described previously, applicationsaccessing NUMA domains will operate within a certain range of memoryaddresses in that NUMA domain. As such, by appropriately specifying agranularity, it may yield a more accurate prediction, resulting in ahigh hit rate, as well as return a result within a few cycles.Accordingly, in some embodiments, to predict the NUMA domain of athrottling message targeting a particular address and a particular agententity, the throttling message transmission module 430 may be configuredto access the domain prediction table to retrieve the predicted NUMAdomain as a content-addressable memory (CAM) structure. For example, ifa use case for an application is to allocate a 10 GB memory block of astorage node 112 via memory exposed as a NUMA domain, the domainprediction requests would most likely hit on the prediction table if thegranularity chosen is GM.

In some embodiments, the flow for a throttling message to a particularaddress to a particular agent entity may include determining a modulusof the last memory address and the granularity to predict the NUMAdomain to which the last memory address belongs. If the predicted NUMAdomain request returns NULL (i.e., none of the NUMA domains matched)then it may be assumed the closest NUMA domain is NUMA level 0. Asdescribed previously, the processor core does not send transactions tothe agent entity when a distress signal for the NUMA domain is activeand only issues transactions after the distress signal is deactivatedand acknowledged by the agent entity. Accordingly, if the distresssignal is active for the predicted NUMA domain result, the processorcore does not send transactions to the agent entity until the distresssignal is deactivated and acknowledged by the agent entity.Additionally, in some embodiments, the agent entity may perform thesystem address decoding, update appropriate counters (e.g., throttlingrequest counters), and generate the distress signal as necessary.Further, the prediction table is updated according to feedback receivedupon the agent entity having returned an acknowledgement and a NUMAdomain identifier for that specific domain prediction request.

It should be appreciated that the targeted fiber architecture for theQoS-based throttling scheme described herein is directed towardenterprise systems with a scale of hundreds of network nodes 102.Accordingly, in such embodiments with a greater scale, such as a scaleof thousands of nodes of high performance computing (HPC) embodiments,the multicast mode may not be ideal for implementation due to thevoluminous amount of messages that may be transmitted therein. However,sub-domains of network nodes 102 (e.g., consisting of only those networknodes 102 connected to a specific network switch 116) of the fabricarchitecture may be defined, such as by using specific multicasttopologies, in order to propagate the throttling message to only asubset of the network nodes 102. It should be further appreciated thatthe multicast mode may be a non-reliable multicast. As describedpreviously, the throttling messages are transmitted periodically overthe duration of time in which the throttling condition exists, therebynegating the need to acknowledge the receipt of the throttling messages.The reliability may be improved, such as by adding receiptacknowledgements into the flow; however, such reliability improvement islikely to add more pressure into the fabric.

In some embodiments, the throttling message transmission module 430(e.g., the throttling condition detection module 432 and/or thetransmission mode determination module 434) may utilize a requestmonitoring table to determine when a throttling message is to begenerated and/or to which network nodes 102 the generated throttlingmessage is to be sent. In an illustrative example, the throttlingmessage transmission module 430 may be configured to account forexternal transactions targeting the local NUMA domain 300 of aparticular network node 102. As described previously, each of the NUMAdomains 300 has a corresponding NUMA domain identifier usable by thethrottling message transmission module 430 to determine which NUMAdomain 300 a received throttling message corresponds, as well as arequest counter that is incremented with each access.

In some embodiments, the NUMA domain identifier, a value of the requestcounter, as well as other values (e.g., enumerated values of throttlingmessage request types) may be stored in model-specific registers (MSRs).Accordingly, the throttling message transmission module 430 may beconfigured to read a value of the request counter to determine whetherthe request counter exceeds a threshold value. It should be appreciatedthat the MSR values can be configured during operation or boot time(e.g., using ring zero functions), and may be exposed to the operatingsystem of the network node 102.

In some embodiments, the request counter may be stored in the requestmonitoring table that includes an identifier of the network node 102from which the throttling message was received, a present value of therequest counter, the NUMA domain identifier, and the threshold value. Insome embodiments, the data of the request monitoring table may be storedin the request monitoring data 406. If the request counter exceeds athreshold value, the throttling message transmission module 430 may beconfigured to generate a throttling message for transmission in unicastmode (i.e., to just the network node 102 responsible for the presentstate of the request counter). Additionally, the throttling messagetransmission module 430 may be configured to generate a throttlingmessage for transmission in multicast mode (i.e., to all the othernetwork nodes 102 issuing transactions to a particular NUMA domain) uponreceiving a throttling signal internally, such as from a caching agent.As described previously, the throttling message transmission module 430is configured to generate the throttling message periodically while thethrottling condition is detected.

It should be appreciated that the system configurations, such as theNUMA domain identifiers, MSRs in the different network nodes 102, etc.,should be done holistically to ensure coherency. Accordingly, the systemconfigurations should be enforced at system boot time (e.g., when therouting system address decoding scheme is performed) to ensure thatinformation conveyed in the throttling messages is consistent across thedifferent network nodes 102. For example, in an embodiment wherein NUMAdomain identifiers for compute node (1) 106 are being propagated tocompute node (2) 108, compute node (2) 108 should already be aware ofwhich NUMA domain identifier corresponds to the particular NUMA domain300 of the compute node (1) 106. In some embodiments, the NUMA domainidentifiers of the other network nodes 102 may be stored in the NUMAidentification data 408.

The throttling message reception module 440, which may be embodied ashardware, firmware, software, virtualized hardware, emulatedarchitecture, and/or a combination thereof as discussed above, isconfigured to receive and process throttling messages from the othernetwork nodes 102. To do so, the illustrative throttling messagereception module 440 includes a throttling type identification module442 and a NUMA target identification module 444. It should beappreciated that each of the throttling type identification module 442and the NUMA target identification module 444 of the throttling messagereception module 440 may be separately embodied as hardware, firmware,software, virtualized hardware, emulated architecture, and/or acombination thereof. For example, the throttling type identificationmodule 442 may be embodied as a hardware component, while the NUMAtarget identification module 444 is embodied as a virtualized hardwarecomponent or as some other combination of hardware, firmware, software,virtualized hardware, emulated architecture, and/or a combinationthereof.

The throttling type identification module 442 is configured to identifya type associated with the received throttling message. As describedpreviously, the throttling message request types associated with thethrottling messages may include a memory throttle request, an I/Othrottle request, an accelerator throttle processing request, an HFIsaturation throttle request, etc. In some embodiments, the throttlingmessage request types may be enumerated such that they can be mapped toa particular action. Additionally, some embodiments, the enumeratedvalues of the throttling message request types may be stored in athrottle action table that maps the enumerated values to thecorresponding action. The NUMA target identification module 444 isconfigured to identify a NUMA domain target, or component thereof,associated with the received throttling message.

The throttling response execution module 450, which may be embodied ashardware, firmware, software, virtualized hardware, emulatedarchitecture, and/or a combination thereof as discussed above, isconfigured to take an action in response to having received a throttlingmessage from another network node 102. To do so, the illustrativethrottling response execution module 450 includes a processor corethrottling execution module 452, a software interrupt execution module454, and an HFI throttling execution module 456. It should beappreciated that each of the processor core throttling execution module452, the software interrupt execution module 454, and the HFI throttlingexecution module 456 of the throttling response execution module 450 maybe separately embodied as hardware, firmware, software, virtualizedhardware, emulated architecture, and/or a combination thereof. Forexample, the processor core throttling execution module 452 may beembodied as a hardware component, while the software interrupt executionmodule 454 and/or the HFI throttling execution module 456 may beembodied as a virtualized hardware component or as some othercombination of hardware, firmware, software, virtualized hardware,emulated architecture, and/or a combination thereof.

The processor core throttling execution module 452 is configured tothrottle processor cores in response to receiving a propagatedthrottling message. To do so, the processor core throttling executionmodule 452 is configured to translate a received throttling message tocorresponding on-die interconnect throttling signals supported by thenetwork node 102 architecture to reduce an injection rate of externallytransmitted access requests. The software interrupt execution module 454is configured to perform a software interrupt in response to havingreceived a software interrupt request throttling message. To do so, thethrottling message is propagated to the software stack via a softwareinterrupt in such embodiments wherein the software stack supports loadbalancing and injection control mechanisms.

The HFI throttling execution module 456 is configured to throttleinjections at the HFI 222 based on the type of throttling messagereceived. In other words, the HFI 222 is responsible for reducing theinjection rate or stopping the injection altogether. Accordingly, such aresponse may be a suitable solution for throttle message types notsupported by the fabric architecture of the network nodes 102. It shouldbe appreciated that the processor cores and other injectors of thenetwork node 102 are not being throttled.

Referring now to FIG. 5 , in use, a network node 102 (e.g., one of thenetwork nodes 102 of FIG. 1 ) may execute a method 500 for processing alocal memory request from a remote network node (i.e., another one ofthe network nodes 102 of the fabric architecture). The method 500 beginsin block 502, in which the network node 102 determines whether a memoryaccess request has been received from a remote network node. If not, themethod 500 loops back to block 502 to determine whether a memory accessrequest has been received from a remote network node; otherwise, themethod 500 advances to block 504. In block 504, the network node 102inserts the received remote memory access request into a shared bufferof the network node 102. It should be appreciated that, under certainconditions, the shared buffer may be full for a period of time beforethe network node 102 can insert the received remote memory accessrequest into the shared buffer.

In block 506, the network node 102 determines whether to process thereceived request (e.g., pop the corresponding entry from the sharedbuffer and process the request). If so, the method 500 advances to block508, in which the network node 102 performs an action in response to thereceived remote memory access request. For example, in block 510, thenetwork node 102 may transmit request data in response to a remotememory access request having requested data stored in memory (e.g., themain memory 216) of the network node 102. Alternatively, in block 512,the network node 102 may store data received with the remote memoryaccess request. In some embodiments, in block 514, the network node 102may transmit an acknowledgement in response to having received/processedthe remote memory access request.

Referring now to FIG. 6 , in use, a network node 102 (e.g., one of thenetwork nodes 102 of FIG. 1 ) may execute a method 600 for accessingmemory of a remote network node (i.e., another one of the network nodes102 of the fabric architecture). The method 600 begins in block 602, inwhich the network node 102 determines whether to access memory locatedin another network node 102. For example, the network node 102 may beretrieving data replicated in remote memory (i.e., memory of the remotenetwork node), executing an application utilizing distributed datastructures on one or more remote network nodes, employing log shipping(i.e., relying on a log or micro-log stored on the remote network nodefor failure recovery), or performing some other operation that requiresaccessing memory of a remote network node.

If not, the method 600 loops back to block 602 to again determinewhether to access memory located in another network node 102; otherwise,the method 600 advances to block 604. In block 604, the network node 102generates a remote memory access request that includes memory addressinformation usable to retrieve or store data of the remote memory accessrequest. Additionally, in block 606, the network node 102 includessource identifying information of the network node 102. In block 608,the network node 102 inserts the memory access request into a messagetransmission queue.

In block 610, the network node 102 determines whether an injection ratecorresponding to the component(s) from which the remote memory accessrequest is requesting access has been throttled as a result ofthrottling messages received from the remote network node (see, e.g.,the method 700 of FIG. 7 directed toward generating throttling messagesfor external transmission to one or more remote network nodes). If not,the method 600 branches to block 612, in which the network node 102transmits the remote memory access request at a non-throttled injectionrate; otherwise, the method 600 branches to block 614, in which thenetwork node 102 transmits the remote memory access request at athrottled rate.

Referring now to FIG. 7 , in use, a network node 102 (e.g., one of thenetwork nodes 102 of FIG. 1 ) may execute a method 700 for generatingthrottling messages for external transmission to one or more remotenetwork nodes (i.e., one or more of the other network nodes 102). Themethod 700 begins in block 702, in which the network node 102 monitorsquality of service levels of the network node 102. For example, in block704, the network node 102 monitors utilization levels of the resources(e.g., memory, processors, components of a NUMA domain, etc.) of thenetwork node 102, in some embodiments. Additionally or alternatively, inblock 706, the network node 102 monitors the distribution of theworkloads distributed across the components of the network node 102, insome embodiments. In block 708, the network node 102 additionally oralternatively monitors saturation levels of the HFI 222 of the networknode 102, in some embodiments. As described previously, in someembodiments, the network node 102 may rely on a request monitoring tableto determine when the throttling messages are to be generated for aparticular NUMA domain 300.

As also described previously, certain conditions (i.e., throttlingconditions) may exist on the network node 102 such that resource accessrequests generated by the network node 102 requesting access to localresources of the network node 102 may become starved due to remotenetwork nodes 102 maintaining an unencumbered injection rate toresources that are locally throttled. Accordingly, in block 710, thenetwork node 102 determines whether a throttling condition (e.g.,congestion, saturation, over-utilization, workload distributionunfairness, etc., of a component of the network node 102) has beendetected (i.e., presently exists) as a result of the quality of servicemonitoring performed in block 702.

If the network node 102 determines that a throttling condition does notexist, the method 700 loops back to block 702 to continue monitoring thequality of service levels of the network node 102; otherwise, the method700 advances to block 712, in which the network node 102 generates athrottling message. In block 714, the network node 102 includes athrottling message request type indicator with the throttling message.As described previously, the throttling message request types associatedwith the throttling messages may include a memory throttle request, anI/O throttle request, an accelerator throttle processing request, an HFIsaturation throttle request, etc. Additionally, in block 716, thenetwork node 102 includes a throttling message source indicator. Thethrottling message source indicator may include an identifier of thecomponent (e.g., a NUMA domain identifier, an HFI identifier) for whichthe throttling condition has been detected and/or an identifier of thenetwork node 102.

In block 718, the network node 102 identifies one or more target networknodes (i.e., one or more of the other network nodes 102 of the fabricarchitecture) that are to receive the throttling message generated inblock 712. As described previously, in some embodiments, the networknode 102 may rely on a request monitoring table to determine the one ormore target network nodes. In block 720, the network node 102 transmitsthe generated throttling message to the one or more target network nodesidentified in block 718. To do so, in block 722, the network node 102transmits the generated throttling message based on a cycle ratecorresponding to each of the target network nodes.

Depending on the number of target network nodes identified in block 718,the network node 102 may transmit the generated throttling message via amulticast transmission (i.e., more than one target network node) inblock 724, or via a unicast transmission (i.e., a single target networknode) in block 726. Additionally, in some embodiments, in block 728, thenetwork node 102 may transmit the generated throttling message via thetransport layer of the OSI model. To do so, in some embodiments, thefabric may be extended with a new type of virtual channel thatfacilitates the transfer of the throttling messages in order tosegregate the throttling messages from the existing channels of thefabric. Such embodiments may be implemented via a new type of physicalwire that takes fastest paths inside the fabric in order to deliver thethrottling messages as fast as possible.

As described previously, the throttling messages are transmittedperiodically over the course of the detected throttling condition. Assuch, the method 700 may monitor quality of service levels relative tothat specific throttling condition and iterate the method 700 as aresult of that specific quality of service level monitoring.

Referring now to FIG. 8 , in use, a network node 102 (e.g., one of thenetwork nodes 102 of FIG. 1 ) may execute a method 800 for processingthrottling messages received from a remote network node (i.e., one ofthe other network nodes 102). The method 800 begins in block 802, inwhich the network node 102 determines whether a throttling message hasbeen received from a remote network node. If not, the method 800 loopsback to block 802 to again determine whether a throttling message hasbeen received from a remote network node; otherwise, the method 800advances to block 804, in which the network node 102 identifiesinformation associated with the throttling message received in block802.

For example, in block 806, the network node 102 identifies a type of thethrottling message. As described previously, the throttling messagerequest types associated with the throttling messages may include amemory throttle request, an I/O throttle request, an acceleratorthrottle processing request, an HFI saturation throttle request, etc.Additionally, in block 808, the network node 102 identifies a source ofthe throttling message. The source of the throttling message may includeinformation that identifies the target network node from which thethrottling message was received. Additionally, the source of thethrottling message may include a component identifier (e.g., a NUMAidentifier) identifying a component of the remote network node fromwhich the throttling quest was received. In some embodiments, thethrottling message may additionally include component information of thereceiving network node 102 usable to identify which network node 102resources, from which remote memory accesses are being requested, are tobe throttled.

In block 810, the network node 102 performs an action based on thereceived throttling message, such as may be based on the type of thethrottling message identified in block 806. For example, in block 812,the network node 102 may reduce an injection rate for shared resourceaccess requests being transmitted to (i.e., targeting) the remotenetwork node by self-throttling requests by the HFI 222 of the networknode 102. In another example, in block 814, the network node 102 maythrottle processor cores of the network node 102 by using the existingthrottling schemes. To do so, the network node 102 may propagate thereceived throttling message to an agent entity (e.g., a caching agent)via a corresponding on-die interconnect (e.g., the on-die interconnect306 of the processor 202, the on-die interconnect 312 of the processor208, etc.) to throttle processor cores of the network node 102 by usingthe existing throttling schemes. In still another example, in block 816,in such embodiments wherein the software stack supports load balancingand injection control mechanisms, the network node 102 may propagate thereceived throttling message to a software stack via a softwareinterrupt.

It should be appreciated that at least a portion of one or more of themethods 500, 600, 700, and 800 may be executed by the HFI 222 of thenetwork nodes 102. It should be further appreciated that, in someembodiments, one or more of the methods 500, 600, 700, and 800 may beembodied as various instructions stored on a computer-readable media,which may be executed by a processor (e.g., the processor 202, theprocessor 208, etc.), the HFI 222, and/or other components of thenetwork nodes 102 to cause the network nodes 102 to perform the methods500, 600, 700, and 800. The computer-readable media may be embodied asany type of media capable of being read by the network nodes 102including, but not limited to, the main memory 216, the data storagedevice 218, a secure memory (not shown) of the HFI 222, other memory ordata storage devices of the network nodes 102, portable media readableby a peripheral device of the network nodes 102, and/or other media.

EXAMPLES

Illustrative examples of the technologies disclosed herein are providedbelow. An embodiment of the technologies may include any one or more,and any combination of, the examples described below.

Example 1 includes a network node for quality of service basedthrottling in a fabric architecture in which the network node is one ofa plurality of interconnected network nodes of the fabric architecture,the network node comprising a processor; a host fabric interface (HFI)to facilitate the transmission of data between the plurality ofinterconnected network nodes over an interconnect fabric of the fabricarchitecture; and one or more data storage devices having stored thereina plurality of instructions that, when executed by the processor, causethe network node to monitor quality of service levels of the networknode; detect a throttling condition based on a result of the monitoredquality of service levels; generate, in response to having detected thethrottling condition, a throttling message based on a request typeassociated with the throttling condition detected; and transmit thegenerated throttling message to one or more of the plurality ofinterconnected network nodes communicatively coupled to the network nodevia the interconnect fabric.

Example 2 includes the subject matter of Example 1, and wherein tomonitor quality of service levels of the network node comprises tomonitor utilization levels of one or more resources of the network node.

Example 3 includes the subject matter of any of Examples 1 and 2, andwherein the one or more resources of the network node include at leastone of the processor, the one or more data storage devices, or the HFI.

Example 4 includes the subject matter of any of Examples 1-3, andwherein the one or more resources of the network node include aplurality of non-uniform memory access (NUMA) domains, wherein each ofthe plurality of NUMA domains includes an allocated portion of processorcores of the processor and an allocated portion of the one or more datastorage devices, and wherein each of the plurality of NUMA domains iscommunicatively coupled to the HFI via an on-die interconnect of theprocessor.

Example 5 includes the subject matter of any of Examples 1-4, andwherein to monitor the quality of service levels of the network nodecomprises to monitor a workload distribution.

Example 6 includes the subject matter of any of Examples 1-5, andwherein to monitor the quality of service levels of the network nodecomprises to monitor a saturation level of the HFI.

Example 7 includes the subject matter of any of Examples 1-6, andwherein to monitor the quality of service levels of the network nodecomprises to monitor throttling signals received from an agent entity ofthe processor.

Example 8 includes the subject matter of any of Examples 1-7, andwherein the plurality of interconnected network nodes includes one ormore compute nodes and one or more storage nodes.

Example 9 includes the subject matter of any of Examples 1-8, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to one of the plurality ofinterconnected network nodes via a unicast transmission.

Example 10 includes the subject matter of any of Examples 1-9, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to more than one of the plurality ofinterconnected network nodes via a multicast transmission.

Example 11 includes the subject matter of any of Examples 1-10, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to the one or more of the plurality ofinterconnected network nodes via a transport layer of the Open SystemsInterconnection (OSI) model.

Example 12 includes the subject matter of any of Examples 1-11, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to the one or more of the plurality ofinterconnected network nodes at a periodic injection rate for a durationof the detected throttling condition.

Example 13 includes a network node for quality of service basedthrottling in a fabric architecture in which the network node is one ofa plurality of interconnected network nodes of the fabric architecture,the network node comprising a quality of service monitoring circuit tomonitor quality of service levels of the network node between a hostfabric interface (HFI) of the network node and one or more HFIs of theother interconnected network nodes over an interconnect fabric of thefabric architecture; a throttling message transmission circuit to (i)detect a throttling condition based on a result of the monitored qualityof service levels, (ii) generate, in response to having detected thethrottling condition, a throttling message based on a request typeassociated with the throttling condition detected, and (iii) transmitthe generated throttling message to one or more of the plurality ofinterconnected network nodes communicatively coupled to the network nodevia the interconnect fabric.

Example 14 includes the subject matter of Example 13, and wherein tomonitor quality of service levels of the network node comprises tomonitor utilization levels of one or more resources of the network node.

Example 15 includes the subject matter of any of Examples 13 and 14, andwherein the one or more resources of the network node include at leastone of a processor of the network node, one or more data storage devicesof the network node, or the HFI.

Example 16 includes the subject matter of any of Examples 13-15, andwherein the one or more resources of the network node include aplurality of non-uniform memory access (NUMA) domains, wherein each ofthe plurality of NUMA domains includes an allocated portion of processorcores of the processor and an allocated portion of the one or more datastorage devices, and wherein each of the plurality of NUMA domains iscommunicatively coupled to the HFI via an on-die interconnect of theprocessor.

Example 17 includes the subject matter of any of Examples 13-16, andwherein to monitor the quality of service levels of the network nodecomprises to monitor a workload distribution.

Example 18 includes the subject matter of any of Examples 13-17, andwherein to monitor the quality of service levels of the network nodecomprises to monitor a saturation level of the HFI.

Example 19 includes the subject matter of any of Examples 13-18, andwherein to monitor the quality of service levels of the network nodecomprises to monitor throttling signals received from an agent entity ofthe processor.

Example 20 includes the subject matter of any of Examples 13-19, andwherein the plurality of interconnected network nodes includes one ormore compute nodes and one or more storage nodes.

Example 21 includes the subject matter of any of Examples 13-20, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to one of the plurality ofinterconnected network nodes via a unicast transmission.

Example 22 includes the subject matter of any of Examples 13-21, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to more than one of the plurality ofinterconnected network nodes via a multicast transmission.

Example 23 includes the subject matter of any of Examples 13-22, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to the one or more of the plurality ofinterconnected network nodes via a transport layer of the Open SystemsInterconnection (OSI) model.

Example 24 includes the subject matter of any of Examples 13-23, andwherein to transmit the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises to transmitthe generated throttling message to the one or more of the plurality ofinterconnected network nodes at a periodic injection rate for a durationof the detected throttling condition.

Example 25 includes a method for quality of service based throttlingacross a fabric architecture, the method comprising monitoring, by ahost fabric interface (HFI) of a network node of the fabricarchitecture, quality of service levels of the network node, wherein thenetwork node is one of a plurality of interconnected network nodes ofthe fabric architecture, wherein each of the plurality of interconnectednetwork nodes is interconnected over an interconnect fabric of thefabric architecture; detecting, by the HFI, a throttling condition basedon a result of the monitored quality of service levels; generating, bythe HFI, in response to having detected the throttling condition, athrottling message based on a request type associated with thethrottling condition detected; and transmitting, by the HFI, thegenerated throttling message to one or more of the plurality ofinterconnected network nodes communicatively coupled to the network nodevia the interconnect fabric.

Example 26 includes the subject matter of Example 25, and whereinmonitoring the quality of service levels of the network node comprisesmonitoring utilization levels of one or more resources of the networknode.

Example 27 includes the subject matter of any of Examples 25 and 26, andwherein monitoring the utilization levels of one or more resources ofthe network node comprises monitoring at least one of a processor of thenetwork node, one or more data storage devices of the network node, orthe HFI.

Example 28 includes the subject matter of any of Examples 25-27, andwherein monitoring the utilization levels of one or more resources ofthe network node comprises monitoring one or more of a plurality ofnon-uniform memory access (NUMA) domains, wherein each of the pluralityof NUMA domains includes an allocated portion of processor cores of aprocessor of the network node and an allocated portion of one or moredata storage devices of the network node, and wherein each of theplurality of NUMA domains is communicatively coupled to the HFI via anon-die interconnect of the processor.

Example 29 includes the subject matter of any of Examples 25-28, andwherein monitoring the quality of service levels of the network nodecomprises monitoring a workload distribution.

Example 30 includes the subject matter of any of Examples 25-29, andwherein monitoring the quality of service levels of the network nodecomprises monitoring a saturation level of the HFI.

Example 31 includes the subject matter of any of Examples 25-30, andwherein monitoring the quality of service levels of the network nodecomprises monitoring throttling signals received from an agent entity ofthe processor.

Example 32 includes the subject matter of any of Examples 25-31, andwherein the plurality of interconnected network nodes includes one ormore compute nodes and one or more storage nodes.

Example 33 includes the subject matter of any of Examples 25-32, andwherein transmitting the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises transmittingthe generated throttling message to one of the plurality ofinterconnected network nodes via a unicast transmission.

Example 34 includes the subject matter of any of Examples 25-33, andwherein transmitting the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises transmittingthe generated throttling message to more than one of the plurality ofinterconnected network nodes via a multicast transmission.

Example 35 includes the subject matter of any of Examples 25-34, andwherein transmitting the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises transmittingthe generated throttling message to the one or more of the plurality ofinterconnected network nodes via a transport layer of the Open SystemsInterconnection (OSI) model.

Example 36 includes the subject matter of any of Examples 25-35, andwherein transmitting the generated throttling message to the one or moreof the plurality of interconnected network nodes comprises transmittingthe generated throttling message to the one or more of the plurality ofinterconnected network nodes at a periodic injection rate for a durationof the detected throttling condition.

Example 37 includes a network node comprising a processor; and a memoryhaving stored therein a plurality of instructions that when executed bythe processor cause the network node to perform the method of any ofExamples 25-36.

Example 38 includes one or more machine readable storage mediacomprising a plurality of instructions stored thereon that in responseto being executed result in a network node performing the method of anyof Examples 25-36.

Example 39 includes a network node for quality of service basedthrottling in a fabric architecture in which the network node is one ofa plurality of interconnected network nodes of the fabric architecture,the network node comprising means for monitoring quality of servicelevels of the network node at a host fabric interface (HFI) of thenetwork node, wherein the network node is one of a plurality ofinterconnected network nodes of the fabric architecture, wherein each ofthe plurality of interconnected network nodes is interconnected over aninterconnect fabric of the fabric architecture; means for detecting athrottling condition based on a result of the monitored quality ofservice levels; means for generating in response to having detected thethrottling condition, a throttling message based on a request typeassociated with the throttling condition detected; and means fortransmitting the generated throttling message to one or more of theplurality of interconnected network nodes communicatively coupled to thenetwork node via the interconnect fabric.

Example 40 includes the subject matter of Example 39, and wherein themeans for monitoring the quality of service levels of the network nodecomprises means for monitoring utilization levels of one or moreresources of the network node.

Example 41 includes the subject matter of any of Examples 39 and 40, andwherein the means for monitoring the utilization levels of one or moreresources of the network node comprises means for monitoring at leastone of a processor of the network node, one or more data storage devicesof the network node, or the HFI.

Example 42 includes the subject matter of any of Examples 39-41, andwherein the means for monitoring the utilization levels of one or moreresources of the network node comprises means for monitoring one or moreof a plurality of non-uniform memory access (NUMA) domains, wherein eachof the plurality of NUMA domains includes an allocated portion ofprocessor cores of a processor of the network node and an allocatedportion of one or more data storage devices of the network node, andwherein each of the plurality of NUMA domains is communicatively coupledto the HFI via an on-die interconnect of the processor.

Example 43 includes the subject matter of any of Examples 39-42, andwherein the means for monitoring the quality of service levels of thenetwork node comprises means for monitoring a workload distribution.

Example 44 includes the subject matter of any of Examples 39-43, andwherein the means for monitoring the quality of service levels of thenetwork node comprises means for monitoring a saturation level of theHFI.

Example 45 includes the subject matter of any of Examples 39-44, andwherein the means for monitoring the quality of service levels of thenetwork node comprises means for monitoring throttling signals receivedfrom an agent entity of the processor.

Example 46 includes the subject matter of any of Examples 39-45, andwherein the plurality of interconnected network nodes includes one ormore compute nodes and one or more storage nodes.

Example 47 includes the subject matter of any of Examples 39-46, andwherein the means for transmitting the generated throttling message tothe one or more of the plurality of interconnected network nodescomprises means for transmitting the generated throttling message to oneof the plurality of interconnected network nodes via a unicasttransmission.

Example 48 includes the subject matter of any of Examples 39-47, andwherein the means for transmitting the generated throttling message tothe one or more of the plurality of interconnected network nodescomprises means for transmitting the generated throttling message tomore than one of the plurality of interconnected network nodes via amulticast transmission.

Example 49 includes the subject matter of any of Examples 39-48, andwherein the means for transmitting the generated throttling message tothe one or more of the plurality of interconnected network nodescomprises means for transmitting the generated throttling message to theone or more of the plurality of interconnected network nodes via atransport layer of the Open Systems Interconnection (OSI) model.

Example 50 includes the subject matter of any of Examples 39-49, andwherein the means for transmitting the generated throttling message tothe one or more of the plurality of interconnected network nodescomprises means for transmitting the generated throttling message to theone or more of the plurality of interconnected network nodes at aperiodic injection rate for a duration of the detected throttlingcondition.

Example 51 includes a network node for quality of service basedthrottling in a fabric architecture in which the network node is one ofa plurality of interconnected network nodes of the fabric architecture,the network node comprising a processor; a host fabric interface (HFI)to facilitate the transmission of data between the plurality ofinterconnected network nodes; and one or more data storage deviceshaving stored therein a plurality of instructions that, when executed bythe processor, cause the network node to transmit an access request foraccess to a shared resource of one of the plurality of interconnectednetwork nodes communicatively coupled to the network node via aninterconnect fabric of the fabric architecture; receive a throttlingmessage from the one of the plurality of interconnected network nodes;identify information associated with the received throttling message;and perform a throttling action on one or more resources of the networknode based in the identified information.

Example 52 includes the subject matter of Example 51, and wherein toreceive the throttling message comprises to receive the throttlingmessage via a transport layer of the Open Systems Interconnection (OSI)model.

Example 53 includes the subject matter of any of Examples 51 and 52, andwherein to identify the information associated with the receivedthrottling message comprises to identify at least one of a request typeof the received throttling message and a source of the receivedthrottling message.

Example 54 includes the subject matter of any of Examples 51-53, andwherein the request type of the received throttling message comprisesone of a memory throttle request, an I/O throttle request, anaccelerator throttle processing request, or an HFI saturation throttlerequest.

Example 55 includes the subject matter of any of Examples 51-54, andwherein to perform the throttling action comprises to reduce aninjection rate of the shared resource access requests directed towardthe one of the plurality of interconnected network nodes.

Example 56 includes the subject matter of any of Examples 51-55, andwherein to perform the throttling action comprises to throttle processorcores of the processor of the network node.

Example 57 includes the subject matter of any of Examples 51-56, andwherein to throttle the processor cores of the processor of the networknode comprises to propagate the received throttling message to an agententity of the processor for translation to an existing throttlingsignal.

Example 58 includes the subject matter of any of Examples 51-57, andwherein to perform the throttling action comprises to propagate thereceived throttling message to a software stack via a softwareinterrupt.

Example 59 includes the subject matter of any of Examples 51-58, andwherein the one or more resources of the network node include at leastone of the processor, the one or more data storage devices, or the HFI.

Example 60 includes the subject matter of any of Examples 51-59, and,wherein the one or more resources of the network node include aplurality of non-uniform memory access (NUMA) domains, wherein each ofthe plurality of NUMA domains includes an allocated portion of processorcores of the processor and an allocated portion of the one or more datastorage devices, and wherein each of the plurality of NUMA domains iscommunicatively coupled to the HFI via an on-die interconnect of theprocessor.

Example 61 includes a network node for quality of service basedthrottling in a fabric architecture in which the network node is one ofa plurality of interconnected network nodes of the fabric architecture,the network node comprising a communication management circuit totransmit an access request for access to a shared resource of one of theplurality of interconnected network nodes communicatively coupled to thenetwork node via an interconnect fabric of the fabric architecture; athrottling message reception circuit to (i) receive a throttling messagefrom a host fabric interface (HFI) of the one of the plurality ofinterconnected network nodes and (ii) identify information associatedwith the received throttling message; and a throttling responseexecution circuit to perform a throttling action on one or moreresources of the network node based in the identified information.

Example 62 includes the subject matter of Example 61, and wherein toreceive the throttling message comprises to receive the throttlingmessage via a transport layer of the Open Systems Interconnection (OSI)model.

Example 63 includes the subject matter of any of Examples 61 and 62, andwherein to identify the information associated with the receivedthrottling message comprises to identify at least one of a request typeof the received throttling message and a source of the receivedthrottling message.

Example 64 includes the subject matter of any of Examples 61-63, andwherein the request type of the received throttling message comprisesone of a memory throttle request, an I/O throttle request, anaccelerator throttle processing request, or an HFI saturation throttlerequest.

Example 65 includes the subject matter of any of Examples 61-64, andwherein to perform the throttling action comprises to reduce aninjection rate of the shared resource access requests directed towardthe one of the plurality of interconnected network nodes.

Example 66 includes the subject matter of any of Examples 61-65, andwherein to perform the throttling action comprises to throttle processorcores of the processor of the network node.

Example 67 includes the subject matter of any of Examples 61-66, andwherein to throttle the processor cores of the processor of the networknode comprises to propagate the received throttling message to an agententity of the processor for translation to an existing throttlingsignal.

Example 68 includes the subject matter of any of Examples 61-67, andwherein to perform the throttling action comprises to propagate thereceived throttling message to a software stack via a softwareinterrupt.

Example 69 includes the subject matter of any of Examples 61-68, andwherein the one or more resources of the network node include at leastone of the processor, the one or more data storage devices, or the HFI.

Example 70 includes the subject matter of any of Examples 61-69, and,wherein the one or more resources of the network node include aplurality of non-uniform memory access (NUMA) domains, wherein each ofthe plurality of NUMA domains includes an allocated portion of processorcores of the processor and an allocated portion of the one or more datastorage devices, and wherein each of the plurality of NUMA domains iscommunicatively coupled to the HFI via an on-die interconnect of theprocessor.

Example 71 includes a method for quality of service based throttlingacross a fabric architecture, the network node comprising transmitting,by a host fabric interface (HFI) of a network node, an access requestfor access to a shared resource of one of a plurality of interconnectednetwork nodes communicatively coupled to the network node via aninterconnect fabric of the fabric architecture; receiving, by the HFI, athrottling message from the one of the plurality of interconnectednetwork nodes; identifying, by the HFI, information associated with thereceived throttling message; and performing, by the HFI, a throttlingaction on one or more resources of the network node based in theidentified information.

Example 72 includes the subject matter of Example 71, and whereinreceiving the throttling message comprises receiving the throttlingmessage via a transport layer of the Open Systems Interconnection (OSI)model.

Example 73 includes the subject matter of any of Examples 71 and 72, andwherein identifying the information associated with the receivedthrottling message comprises identifying at least one of a request typeof the received throttling message and a source of the receivedthrottling message.

Example 74 includes the subject matter of any of Examples 71-73, andwherein identifying the request type of the received throttling messagecomprises identifying one of a memory throttle request, an I/O throttlerequest, an accelerator throttle processing request, or an HFIsaturation throttle request.

Example 75 includes the subject matter of any of Examples 71-74, andwherein performing the throttling action comprises reducing an injectionrate of the shared resource access requests directed toward the one ofthe plurality of interconnected network nodes.

Example 76 includes the subject matter of any of Examples 71-75, andwherein performing the throttling action comprises throttling processorcores of a processor of the network node.

Example 77 includes the subject matter of any of Examples 71-76, andwherein throttling the processor cores of the processor of the networknode comprises propagating the received throttling message to an agententity of the processor for translation to an existing throttlingsignal.

Example 78 includes the subject matter of any of Examples 71-77, andwherein performing the throttling action comprises propagating thereceived throttling message to a software stack via a softwareinterrupt.

Example 79 includes the subject matter of any of Examples 71-78, andwherein performing the throttling action on the one or more resources ofthe network node comprises performing the throttling action on at leastone of a processor of the network node, one or more data storage devicesof the network node, or the HFI.

Example 80 includes the subject matter of any of Examples 71-79, andwherein performing the throttling action on the one or more resources ofthe network node comprises performing the throttling action on at leastone of a plurality of non-uniform memory access (NUMA) domains, whereineach of the plurality of NUMA domains includes an allocated portion ofprocessor cores of a processor of the network node and an allocatedportion of one or more data storage devices of the network node, andwherein each of the plurality of NUMA domains is communicatively coupledto the HFI via an on-die interconnect of the processor.

Example 81 includes a network node comprising a processor; and a memoryhaving stored therein a plurality of instructions that when executed bythe processor cause the network node to perform the method of any ofExamples 71-80.

Example 82 includes one or more machine readable storage mediacomprising a plurality of instructions stored thereon that in responseto being executed result in a network node performing the method of anyof Examples 71-80.

Example 83 includes a network node for quality of service basedthrottling in a fabric architecture in which the network node is one ofa plurality of interconnected network nodes of the fabric architecture,the network node comprising means for transmitting, by a host fabricinterface (HFI) of the network node, an access request for access to ashared resource of one of a plurality of interconnected network nodescommunicatively coupled to the network node via an interconnect fabricof the fabric architecture; means for receiving, by the HFI, athrottling message from the one of the plurality of interconnectednetwork nodes; means for identifying, by the HFI, information associatedwith the received throttling message; and means for performing, by theHFI, a throttling action on one or more resources of the network nodebased in the identified information.

Example 84 includes the subject matter of Example 83, and wherein themeans for receiving the throttling message comprises means for receivingthe throttling message via a transport layer of the Open SystemsInterconnection (OSI) model.

Example 85 includes the subject matter of any of Examples 83 and 84, andwherein the means for identifying the information associated with thereceived throttling message comprises means for identifying at least oneof a request type of the received throttling message and a source of thereceived throttling message.

Example 86 includes the subject matter of any of Examples 83-85, andwherein the means for identifying the request type of the receivedthrottling message comprises means for identifying one of a memorythrottle request, an I/O throttle request, an accelerator throttleprocessing request, or an HFI saturation throttle request.

Example 87 includes the subject matter of any of Examples 83-86, andwherein the means for performing the throttling action comprises meansfor reducing an injection rate of the shared resource access requestsdirected toward the one of the plurality of interconnected networknodes.

Example 88 includes the subject matter of any of Examples 83-87, andwherein the means for performing the throttling action comprises meansfor throttling processor cores of a processor of the network node.

Example 89 includes the subject matter of any of Examples 83-88, andwherein the means for throttling the processor cores of the processor ofthe network node comprises means for propagating the received throttlingmessage to an agent entity of the processor for translation to anexisting throttling signal.

Example 90 includes the subject matter of any of Examples 83-89, andwherein the means for performing the throttling action comprises meansfor propagating the received throttling message to a software stack viaa software interrupt.

Example 91 includes the subject matter of any of Examples 83-90, andwherein the means for performing the throttling action on the one ormore resources of the network node comprises means for performing thethrottling action on at least one of a processor of the network node,one or more data storage devices of the network node, or the HFI.

Example 92 includes the subject matter of any of Examples 83-91, andwherein the means for performing the throttling action on the one ormore resources of the network node comprises means for performing thethrottling action on at least one of a plurality of non-uniform memoryaccess (NUMA) domains, wherein each of the plurality of NUMA domainsincludes an allocated portion of processor cores of a processor of thenetwork node and an allocated portion of one or more data storagedevices of the network node, and wherein each of the plurality of NUMAdomains is communicatively coupled to the HFI via an on-die interconnectof the processor.

1-23. (canceled)
 24. A method for quality of service (QoS) basedthrottling across a fabric architecture, the method comprising:monitoring QoS levels of a network node, the network node comprising oneof a plurality of interconnected network nodes communicatively coupledvia an interconnect fabric of the fabric architecture; detecting athrottling condition based on a result of the monitored QoS levels;generating, in response to having detected the throttling condition, athrottling message based on a request type associated with thethrottling condition detected, wherein the throttling message is usableby a receiving network node to identify a throttling action based on therequest type; and transmitting, by a host fabric interface (HFI) of thenetwork node, the generated throttling message to one or more of theplurality of interconnected network nodes via the interconnect fabric.25. The method for claim 24, wherein monitoring QoS levels of thenetwork node comprises monitoring utilization levels of one or moreresources of the network node, the one or more resources including atleast a resource associated with one or more processors of the networknode, one or more data storage devices of the network node, or the HFI.26. The method of claim 25, wherein the one or more resources of thenetwork node include a plurality of nonuniform memory access (NUMA)domains, wherein each of the plurality of NUMA domains includes anallocated portion of processor cores of the one or more processor and anallocated portion of the one or more data storage devices, and whereineach of the plurality of NUMA domains is communicatively coupled to theHFI via an on-die interconnect of the processor.
 27. The method of claim24, wherein monitoring the QoS levels of the network node comprisesmonitoring at least one of a workload distribution, a saturation levelof the HFI, or throttling signals received from an agent entity of aprocessor of the network node.
 28. The method of claim 24, wherein theplurality of interconnected network nodes includes one or more computenodes and one or more storage nodes.
 29. The method of claim 24, whereintransmitting the generated throttling message to the one or more of theplurality of interconnected network nodes comprises: transmitting thegenerated throttling message to one of the plurality of interconnectednetwork nodes via a unicast transmission; or transmitting the generatedthrottling message to more than one of the plurality of interconnectednetwork nodes via a multicast transmission.
 30. The method of claim 24,further comprising transmitting the generated throttling message to oneor more of the plurality of interconnected network nodes at a periodicinjection rate for a duration of the detected throttling condition. 31.One or more non-transitory, machine-readable storage media comprising aplurality of instructions stored thereon that, when executed, cause anetwork node to: monitor QoS levels of the network node, the networknode comprising one of a plurality of interconnected network nodescommunicatively coupled via an interconnect fabric of a fabricarchitecture; detect a throttling condition based on a result of themonitored QoS levels; generate, in response to having detected thethrottling condition, a throttling message based on a request typeassociated with the throttling condition detected, wherein thethrottling message is usable by a receiving network node to identify athrottling action based on the request type; and transmit, by a hostfabric interface (HFI) of the network node, the generated throttlingmessage to one or more of the plurality of interconnected network nodesvia the interconnect fabric.
 32. The one or more non-transitory,machine-readable storage media of claim 31, wherein to monitor QoSlevels of the network node comprises monitoring utilization levels ofone or more resources of the network node, the one or more resourcesincluding at least a resource associated with one or more processors ofthe network node, one or more data storage devices of the network node,or the HFI.
 33. The one or more non-transitory, machine-readable storagemedia of claim 32, wherein the one or more resources of the network nodeinclude a plurality of nonuniform memory access (NUMA) domains, whereineach of the plurality of NUMA domains includes an allocated portion ofprocessor cores of the one or more processor and an allocated portion ofthe one or more data storage devices, and wherein each of the pluralityof NUMA domains is communicatively coupled to the HFI via an on-dieinterconnect of the processor.
 34. The one or more non-transitory,machine-readable storage media of claim 31, wherein to monitor the QoSlevels of the network node comprises monitoring at least one of aworkload distribution, a saturation level of the HFI, or throttlingsignals received from an agent entity of a processor of the networknode.
 35. The one or more non-transitory, machine-readable storage mediaof claim 31, wherein the plurality of interconnected network nodesincludes one or more compute nodes and one or more storage nodes. 36.The one or more non-transitory, machine-readable storage media of claim31, wherein to transmit the generated throttling message to the one ormore of the plurality of interconnected network nodes comprises:transmitting the generated throttling message to one of the plurality ofinterconnected network nodes via a unicast transmission; or transmittingthe generated throttling message to more than one of the plurality ofinterconnected network nodes via a multicast transmission.
 37. The oneor more non-transitory, machine-readable storage media of claim 31,wherein the network node is further to transmit the generated throttlingmessage to one or more of the plurality of interconnected network nodesat a periodic injection rate for a duration of the detected throttlingcondition.
 38. A system comprising: an interconnect fabric tocommunicatively couple a plurality of interconnected network nodes of afabric architecture; a first network node of the plurality ofinterconnected network nodes to: monitor quality of service (QoS) levelsof the first network node; detect a throttling condition based on aresult of the monitored QoS levels; generate, in response to havingdetected the throttling condition, a throttling message based on arequest type associated with the throttling condition detected, whereinthe throttling message is usable by a receiving network node to identifya throttling action based on the request type; and transmit, by a hostfabric interface (HFI) of the first network node, the generatedthrottling message to one or more of the plurality of interconnectednetwork nodes via the interconnect fabric.
 39. The system of claim 38,further comprising: a second network node of the plurality ofinterconnected network nodes to: receive the generated throttlingmessage from the first network node; identify information associatedwith the received throttling message including a first throttlingaction; and perform the first throttling action on one or more resourcesof the second network node.
 40. The system of claim 39, wherein thethrottling message is transmitted and received via a transport layer ofan Open Systems Interconnection (OSI) model.
 41. The system of claim 39,wherein the HFI of the first network node is to transmit the generatedthrottling message to the one or more of the plurality of interconnectednetwork nodes at a periodic injection rate for a duration of thedetected throttling condition.
 42. The system of claim 41, wherein theHFI of the first network node is to stop transmission of the generatedthrottling message to the one or more plurality of interconnectednetwork nodes after the throttling condition is no longer detected. 43.The system of claim 42, wherein the second network node is to stopperformance of the first throttle action on the one or more resourceswhen a predetermined period of time has elapsed after the second networknode is no longer receiving the generated throttling message from thefirst network node.
 44. The system of claim 39, wherein the secondnetwork node is to identify at least one of a request type of thereceived throttling message and a source of the received throttlingmessage from the received throttle message.
 45. The system of claim 44,wherein the request type of the received throttling message comprisesone of a memory throttle request, an I/O throttle request, anaccelerator throttle processing request, or an HFI saturation throttlerequest.
 46. The system of claim 39, wherein the first throttling actioncomprises at least one of reducing an injection rate of a sharedresource access request directed to the first network node, propagatingthe received throttling message to a software stack via a softwareinterrupt, or to generate a throttling signal to throttle one or moreprocessor cores of a processor of the second network node.
 47. Thesystem of claim 39, wherein the one or more resources of the secondnetwork node include a plurality of non-uniform memory access (NUMA)domains, each of the plurality of NUMA domains including an allocatedportion of processor cores of a processor of the second network node andan allocated portion of one or more data storage devices of theprocessor.
 48. The system of claim 47, wherein each of the plurality ofNUMA domains is communicatively coupled to a HFI of the second networknode via an on-die interconnect of the processor.